Synchronization signal transmission and reception for radio system

ABSTRACT

An access node comprises node processor circuitry and a node transmitter. The node processor circuitry is configured to generate plural types of synchronization signal blocks for at least partially interspersed transmission over a radio interface. Each synchronization signal block type comprises a unique combination of differing types of information. The node transmitter circuitry configured to at least partially intersperse transmission of the plural types of synchronization signal blocks over the radio interface to at least one wireless terminal. The wireless terminal comprises a terminal receiver and terminal processor circuitry. The terminal receiver is configured to receive, in at least partially interspersed manner, synchronization signal blocks of differing types over a radio interface from an access node. The terminal processor circuitry is configured determine to which of plural types of synchronization signal blocks a received synchronization signal block belongs.

This application claims the priority and benefit of U.S. ProvisionalPatent Application 62/454,016, filed Feb. 2, 2017, entitledSYNCHRONIZATION SIGNAL TRANSMISSION AND RECEPTION FOR RADIO SYSTEM,which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

The technology relates to wireless communications, and particularly tomethods and apparatus for transmitting and receiving system information(SI) in wireless communications.

BACKGROUND

In wireless communication systems, a radio access network generallycomprises one or more access nodes (such as a base station) whichcommunicate on radio channels over a radio or air interface with pluralwireless terminals. In some technologies such a wireless terminal isalso called a User Equipment (UE). A group known as the 3rd GenerationPartnership Project (“3GPP”) has undertaken to define globallyapplicable technical specifications and technical reports for presentand future generation wireless communication systems. The 3GPP Long TermEvolution (“LTE”) and 3GPP LTE Advanced (LTE-A) are projects to improvean earlier Universal Mobile Telecommunications System (“UMTS”) mobilephone or device standard in a manner to cope with future requirements.

Work has started in the International Telecommunications Union (ITU) and3GPP to develop requirements and specifications for new radio (NR) 5Gsystems, e.g., fifth generation systems. Within the scope of 3GPP, a newstudy item (SID) “Study on New Radio Access Technology” has beenapproved. The timeline and the study situations of NR development aresummarized in RP-161596, “Revision of SI: Study on New Radio AccessTechnology”, 3GPP TSG RAN Meeting #73, New Orleans, Sep. 19-22, 2016,which is incorporated herein by reference. In order to fulfill 5Grequirements, changes with regard to 4G LTE system have been proposedfor study, such as higher frequency spectrum usage (e.g., 6 GHz, 40 GHzor up to 100 GHz), scalable numerology (e.g., different subcarrierspacing (SCS), 3.75 KHz, 7.5 KHz, 15 KHz (current LTE), 30 KHz . . .possibly 480 KHz), beam based initial access (one traditional cell maycontain multiple beams due to the particular beamforming adopted).

Here, three PSS sequences provide identification of cell ID (0-2); andSSS sequences provide identification of cell ID group (0-167).Therefore, in all 168*3=504 PCI IDs are supported in the system. In aRAN1 #87 meeting, it was pointed out that “Number of IDs provided byNR-PSS/SSS” should be studied. See, e.g., 3GPP RAN1 #87 Chairman'sNotes, which is incorporated herein by reference. Further, in RAN1 #86meeting, it was agreed that “Detection of NR cell and its ID. See, e.g.,3GPP RAN1 #86 Chairman's Notes, which is incorporated herein byreference.

It is anticipated that in the next generation new radio (NR) technology,a cell corresponds one or multiple transmission and reception point(TRPs). This means multiple TRPs can share the same NR cell ID, or eachtransmission and reception point (TRP) may have its own identifier.Further, the transmission of one TRP can be in the form of single beamor multiple beams. Each of the beams may also possibly have its ownidentifier. FIG. 2 provides a simple example depiction of a relationshipbetween cell, transmission and reception point (TRP), and beam.

It has been agreed in RAN1 #86bis meeting (See, e.g., 3GPP RAN1 #86bisChairman's Notes, which is incorporated herein by reference) that:

-   -   PSS, SSS and/or PBCH can be transmitted within a ‘SS block’        -   Multiplexing other signals are not precluded within a ‘SS            block’    -   One or multiple ‘SS block(s)’ compose an ‘SS burst’    -   One or multiple ‘SS burst(s)’ compose a ‘SS burst set’        -   The Number of SS bursts within a SS burst set is finite.    -   From RAN1 specification perspective, NR air interface defines at        least one periodicity of SS burst set (Note: Interval of SS        burst can be the same as interval of SS burst set in some cases,        e.g., single beam operation)

FIG. 3 is an example NR SS block structure according to the RAN1 #86bismeeting. In FIG. 3, “synchronization signal bursts series” represents a“SS burst set”. Additional detailed examples are illustrated inR1-1610522, “WF on the unified structure of DL sync signal”, IntelCorporation, NTT DOCOMO, ZTE, ZTE Microelectronics, ETRI, InterDigital,Lisbon, Portugal, 10-14 Oct. 2016, which is incorporated herein byreference. According to R1-1611268, “Considerations on SS block design”,ZTE, ZTE Microelectronics, Reno, USA, November 2016, 14-18, 2016, whichis incorporated herein by reference, the structure of the SS block ofFIG. 3 may be as shown in FIG. 4.

Likely a synchronization signal block will have a fixed multiplexingstructure, which means once the information/signal is decided, each willhave fixed time or/and frequency position(s) in the SS block. HerePSS/SSS and PBCH have different periodicity due to different detectionperformance requirements and different methods to combat channeldistortion

The technology disclosed herein concerns design methods for NRsynchronization, e.g., different types of fixed multiplexing structureSS blocks, as well as new structures and operations for access node andwireless terminal utilizing such new synchronization signal blockstructures.

In one of its aspects the technology disclosed herein concerns a userequipment which comprises receiving circuitry. The receiving circuitryis configured to receive, from a base station apparatus, a radioresource control signaling including information, the information beingused for indicating whether a primary synchronization signal and asecondary synchronization signal and a physical broadcast channel and areference signal for decoding the physical broadcast channel aretransmitted in a block consisting of a constant number of OFDM symbols.The receiving circuitry is further configured to receive, based on theinformation, from the base station apparatus, the block in which theprimary synchronization signal and the secondary synchronization signaland the physical broadcast channel and the reference signal for decodingthe physical broadcast channel are transmitted. The primarysynchronization signal and the secondary synchronization signal are usedfor identifying a physical cell identity, and the physical broadcastchannel is used for carrying System Frame Number information.

In another of its aspects the technology disclosed herein concerns amethod in a user equipment. In a basic mode the method comprisesreceiving, from a base station apparatus, a radio resource controlsignaling including information, the information being used forindicating whether a primary synchronization signal and a secondarysynchronization signal and a physical broadcast channel and a referencesignal for decoding the physical broadcast channel are transmitted in ablock consisting of a constant number of OFDM symbols. The methodfurther comprises receiving, based on the information, from the basestation apparatus, the block in which the primary synchronization signaland the secondary synchronization signal and the physical broadcastchannel and the reference signal for decoding the physical broadcastchannel are transmitted. The primary synchronization signal and thesecondary synchronization signal are used for identifying a physicalcell identity. The physical broadcast channel is used for carryingSystem Frame Number information.

In another of its example aspects the technology disclosed hereinconcerns a base station apparatus comprising transmitting circuitry. Thetransmitting circuitry is configured to transmit, to a user equipment, aradio resource control signaling including information, the informationbeing used for indicating whether a primary synchronization signal and asecondary synchronization signal and a physical broadcast channel and areference signal for decoding the physical broadcast channel are mappedto a block consisting of a constant number of OFDM symbols. Thetransmitting circuitry is further configured to transmit, based on theinformation, to the user equipment, the block to which the primarysynchronization signal and the secondary synchronization signal and thephysical broadcast channel and the reference signal for decoding thephysical broadcast channel are mapped. The primary synchronizationsignal and the secondary synchronization signal are used for identifyinga physical cell identity. The physical broadcast channel is used forcarrying System Frame Number information.

In another of its example aspects the technology disclosed hereinconcerns a method in the base station. In a basic example embodiment andmode the method comprises transmitting, to a user equipment, a radioresource control signaling including information, the information beingused for indicating whether a primary synchronization signal and asecondary synchronization signal and a physical broadcast channel and areference signal for decoding the physical broadcast channel are mappedto a block consisting of a constant number of OFDM symbols. The methodfurther comprises transmitting, based on the information, to the userequipment, the block to which the primary synchronization signal and thesecondary synchronization signal and the physical broadcast channel andthe reference signal for decoding the physical broadcast channel aremapped. The primary synchronization signal and the secondarysynchronization signal are used for identifying a physical cellidentity. The physical broadcast channel is used for carrying SystemFrame Number information.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other objects, features, and advantages of thetechnology disclosed herein will be apparent from the following moreparticular description of preferred embodiments as illustrated in theaccompanying drawings in which reference characters refer to the sameparts throughout the various views. The drawings are not necessarily toscale, emphasis instead being placed upon illustrating the principles ofthe technology disclosed herein.

FIG. 1 is a diagrammatic view showing information utilized in an initialaccess procedure.

FIG. 2 is a diagrammatic view showing an example relationship betweencell, transmission and reception point (TRP), and beam

FIG. 3 is a diagrammatic view showing example NR SS block structureaccording to the RAN1 #86bis meeting.

FIG. 4 is a diagrammatic view showing example structure of the SS blockof FIG. 3.

FIG. 5A-FIG. 5H are schematic views showing an example communicationssystem comprising synchronization signal block generators that generatediffering types of synchronization signal blocks for interspersedtransmission over a radio interface to a wireless terminal.

FIG. 5I is a schematic view showing an example communications systemwherein a wireless terminal obtains a beam identifier (BID) and uses thebeam identifier (BID) to obtain a synchronization signal block timeindex.

FIG. 6 is a diagrammatic view of a basic frame structure showinginclusion of an example synchronization signal block.

FIG. 7A and FIG. 7B are diagrammatic views of synchronization signalblocks according to two differing synchronization signal block types.

FIG. 7C is a diagrammatic view of a synchronization signal block of anon-standard synchronization signal block type in which a field thatotherwise would be allocated to the PBCH2 essentially repeats PSS.

FIG. 7D is a diagrammatic view of a synchronization signal block of anon-standard synchronization signal block type in which a field thatotherwise would be allocated to the PBCH2 instead bears non-SSBinformation.

FIG. 8 is a flowchart showing example basic acts or steps performed bythe access node of FIG. 5A.

FIG. 9 is a flowchart showing example basic acts or steps performed bythe access node of FIG. 5A.

FIG. 10A-FIG. 10C are diagrammatic views showing use of either anexplicit or implicit index for indicating synchronization signal blocktype.

FIG. 11 is a diagrammatic view showing of different schemes forgenerating plural synchronization signal block types for differingfrequency bands.

FIG. 12 is a diagrammatic view showing an association of synchronizationsignal block type with differing system frame numbers (SFN).

FIG. 13 is a diagrammatic view showing a synchronization signal blockburst set comprising synchronization signal block bursts, as well as arelationship between beam identifiers and synchronization signal blocktime indexes.

FIG. 14 is a flowchart showing example, basic acts or steps performed bya synchronization signal block detector that determines synchronizationsignal block time index from a beam identifier.

FIG. 15 is a diagrammatic view showing example electronic machinerywhich may comprise node electronic machinery or terminal electronicmachinery.

DETAILED DESCRIPTION

In the following description, for purposes of explanation and notlimitation, specific details are set forth such as particulararchitectures, interfaces, techniques, etc. in order to provide athorough understanding of the technology disclosed herein. However, itwill be apparent to those skilled in the art that the technologydisclosed herein may be practiced in other embodiments that depart fromthese specific details. That is, those skilled in the art will be ableto devise various arrangements which, although not explicitly describedor shown herein, embody the principles of the technology disclosedherein and are included within its spirit and scope. In some instances,detailed descriptions of well-known devices, circuits, and methods areomitted so as not to obscure the description of the technology disclosedherein with unnecessary detail. All statements herein recitingprinciples, aspects, and embodiments of the technology disclosed herein,as well as specific examples thereof, are intended to encompass bothstructural and functional equivalents thereof. Additionally, it isintended that such equivalents include both currently known equivalentsas well as equivalents developed in the future, i.e., any elementsdeveloped that perform the same function, regardless of structure.

Thus, for example, it will be appreciated by those skilled in the artthat block diagrams herein can represent conceptual views ofillustrative circuitry or other functional units embodying theprinciples of the technology. Similarly, it will be appreciated that anyflow charts, state transition diagrams, pseudocode, and the likerepresent various processes which may be substantially represented incomputer readable medium and so executed by a computer or processor,whether or not such computer or processor is explicitly shown.

As used herein, the term “core network” can refer to a device, group ofdevices, or sub-system in a telecommunication network that providesservices to users of the telecommunications network. Examples ofservices provided by a core network include aggregation, authentication,call switching, service invocation, gateways to other networks, etc.

As used herein, the term “wireless terminal” can refer to any electronicdevice used to communicate voice and/or data via a telecommunicationssystem, such as (but not limited to) a cellular network. Otherterminology used to refer to wireless terminals and non-limitingexamples of such devices can include user equipment terminal, UE, mobilestation, mobile device, access terminal, subscriber station, mobileterminal, remote station, user terminal, terminal, subscriber unit,cellular phones, smart phones, personal digital assistants (“PDAs”),laptop computers, netbooks, tablets, e-readers, wireless modems, etc.

As used herein, the term “access node”, “node”, or “base station” canrefer to any device or group of devices that facilitates wirelesscommunication or otherwise provides an interface between a wirelessterminal and a telecommunications system. A non-limiting example of anaccess node may include, in the 3GPP specification, a Node B (“NB”), anenhanced Node B (“eNB”), a home eNB (“HeNB”), or in the 5G terminology,a gNB or even a transmission and reception point (TRP), or some othersimilar terminology. Another non-limiting example of a base station isan access point. An access point may be an electronic device thatprovides access for wireless terminal to a data network, such as (butnot limited to) a Local Area Network (“LAN”), Wide Area Network (“WAN”),the Internet, etc. Although some examples of the systems and methodsdisclosed herein may be described in relation to given standards (e.g.,3GPP Releases 8, 9, 10, 11, . . . ), the scope of the present disclosureshould not be limited in this regard. At least some aspects of thesystems and methods disclosed herein may be utilized in other types ofwireless communication systems.

As used herein, the term “telecommunication system” or “communicationssystem” can refer to any network of devices used to transmitinformation. A non-limiting example of a telecommunication system is acellular network or other wireless communication system.

As used herein, the term “cellular network” can refer to a networkdistributed over cells, each cell served by at least one fixed-locationtransceiver, such as a base station. A “cell” may be any communicationchannel that is specified by standardization or regulatory bodies to beused for International Mobile Telecommunications-Advanced(“IMTAdvanced”). All or a subset of the cell may be adopted by 3GPP aslicensed bands (e.g., frequency band) to be used for communicationbetween a base station, such as a Node B, and a UE terminal. A cellularnetwork using licensed frequency bands can include configured cells.Configured cells can include cells of which a UE terminal is aware andin which it is allowed by a base station to transmit or receiveinformation.

Here, hierarchical synchronization signals, i.e., primarysynchronization sequences (PSS) and secondary synchronization sequences(SSS) provide coarse time/frequency synchronization, physical layer cellID (PCI) identification, subframe timing identification, frame structuretype (FDD or TDD) differentiation and cyclic prefix (CP) overheadidentification. On the other hand, in such systems, a physical broadcastchannel (PBCH) provides further information, such as system frame number(SFN) and essential system information so that a wireless terminal (e.,UE) can obtain information to access the network. An initial accessprocedure for such system is illustrated in FIG. 1.

Three PSS sequences provide identification of cell ID (0-2); and SSSsequences provide identification of cell ID group (0-167). Therefore, inall 168*3=504 PCI IDs are supported in the system.

As stated in U.S. provisional patent application 62/443,622, filed Jan.6, 2017, incorporated herein by reference in its entirety, a PBCH may beskipped in a SS block, and in such case the resources originally usedfor PBCH in the fixed multiplexing structure can be used for otherpurposes, e.g., used for SS repetition to enhance SS detectionperformance. In some of its example aspects, the technology disclosedherein specifies how a wireless terminal may know which SS block haswhat kind of information skipped in the fixed multiplexing structure,and how the wireless terminal may know its corresponding behavior insuch situation.

FIG. 5A shows an example communications system 20A wherein radio accessnode 22A communicates over air or radio interface 24 (e.g., Uuinterface) with wireless terminal 26. As mentioned above, the radioaccess node 22A may be any suitable node for communicating with thewireless terminal 26, such as a base station node, or eNodeB (“eNB”) orgNodeB or gNB, for example. The node 22A comprises node processorcircuitry (“node processor 30”) and node transceiver circuitry 32. Thenode transceiver circuitry 32 typically comprises node transmittercircuitry 34 and node receiver circuitry 36, which are also called nodetransmitter and node receiver, respectively.

The wireless terminal 26 comprises terminal processor 40 and terminaltransceiver circuitry 42. The terminal transceiver circuitry 42typically comprises terminal transmitter circuitry 44 and terminalreceiver circuitry 46, which are also called terminal transmitter 44 andterminal receiver 46, respectively. The wireless terminal 26 alsotypically comprises user interface 48. The terminal user interface 48may serve for both user input and output operations, and may comprise(for example) a screen such as a touch screen that can both displayinformation to the user and receive information entered by the user. Theuser interface 48 may also include other types of devices, such as aspeaker, a microphone, or a haptic feedback device, for example.

For both the radio access node 22A and radio interface 24, therespective transceiver circuitries 22 include antenna(s). The respectivetransmitter circuits 34 and 44 may comprise, e.g., amplifier(s),modulation circuitry and other conventional transmission equipment. Therespective receiver circuits 36 and 46 may comprise, e.g., e.g.,amplifiers, demodulation circuitry, and other conventional receiverequipment.

In general operation node, access node 22A and wireless terminal 26communicate with each other across radio interface 24 using predefinedconfigurations of information. By way of non-limiting example, the radioaccess node 22A and wireless terminal 26 may communicate over radiointerface 24 using “frames” of information that may be configured toinclude various channels. In Long Term Evolution (LTE), for example, aframe, which may have both downlink portion(s) and uplink portion(s),may comprise plural subframes, with each LTE subframe in turn beingdivided into two slots. The frame may be conceptualized as a resourcegrid (a two dimensional grid) comprised of resource elements (RE). Eachcolumn of the two dimensional grid represents a symbol (e.g., an OFDMsymbol on downlink (DL) from node to wireless terminal; an SC-FDMAsymbol in an uplink (UL) frame from wireless terminal to node). Each rowof the grid represents a subcarrier. The frame and subframe structureserves only as an example of a technique of formatting of informationthat is to be transmitted over a radio or air interface. It should beunderstood that “frame” and “subframe” may be utilized interchangeablyor may include or be realized by other units of information formatting,and as such may bear other terminology (such as blocks, or symbol, slot,mini-slot in 5G for example).

To cater to the transmission of information between radio access node22A and wireless terminal 26 over radio interface 24, the node processor30 and terminal processor 40 of FIG. 1 are shown as comprisingrespective information handlers. For an example implementation in whichthe information is communicated via frames, the information handler forradio access node 22A is shown as node frame/signal scheduler/handler50, while the information handler for wireless terminal 26 is shown asterminal frame/signal handler 52.

In the technology disclosed herein access node 22A comprisessynchronization signal block generator 60. The synchronization signalblock generator 60, which may be realized by node processor 30, servesto generate plural types of synchronization signal blocks for at leastpartially interspersed transmission over the radio interface 24. Eachtype of synchronization signal block comprises a unique combination oftypes of information, as described herein. The transmitter circuitry 34transmits the synchronization signal blocks generated by synchronizationsignal block generator 60 in at least partially interspersed manner overthe radio interface 24. As such, the wireless terminal 26 does notreceive a constant stream of synchronization signal blocks all of thesame type, but from time to time receives one or more synchronizationsignal blocks of differing type in a series of synchronization signalblock transmissions.

The synchronization signal blocks may be carried in a frame structurethat may be realized as an array or grid of time and frequency(carrier/subcarrier) resources. For example, FIG. 6 illustrates a basictransmission frame 62 in which time resources are depicted along an Xaxis and frequency (e.g., subcarriers) are arranged along a Y axis. Anexample synchronization signal block 64 is depicted as being included inthe frame 62. There may be different subcarrier spacing in differentsystems depending on how the frame is constructed. For a givensubcarrier spacing, preferably all synchronization signal blocks have asame size in terms of a same number of resources that comprise thesynchronization signal block. Such same number of resources may bereferred to as the “reference design” of the synchronization signalblock. For example, an integer N number of OFDM symbols may comprise thesynchronization signal blocks for a given subcarrier spacing. Forexample, for a given frequency band, the (a) synchronization signalblock may correspond to N symbols (e.g., OFDM symbols). Here, the numberof N may be a constant. Also, for a given frequency band, a (the)synchronization signal block may correspond to N symbols based on adefault subcarrier spacing. For example, the default subcarrier spacingmay be defined for a given frequency band, in advance, by thespecifications. For example, the default subcarrier spacing may be 15kHz. While preferably the number of resources utilized for asynchronization signal block is fixed, the relative “dimensions” of thesynchronization signal block along the time and frequency axes of thegrid may vary according to differing implementations of the referencedesign.

In the above regard, it should be appreciated from FIG. 4 that contentof a synchronization signal block may be constructed or multiplexedeither in a time division manner, a frequency division manner, or usinga hybrid of time division and frequency division. For example, in thetime divisional (TDM) illustration of FIG. 4 symbols 0-2 may beallocated to a primary synchronization signal (PSS), symbols 3-5 may beallocated to secondary synchronization signal (SSS), and symbols 6-9 maybe allocated to a Physical Broadcast Channel (PBCH). Namely, thesynchronization signal block(s) may comprise of one or more symbolscorresponding to the signal(s) and/or the channel(s).

As indicated above, the synchronization signal block generator 60generates plural types of synchronization signal blocks, and each typeof synchronization signal block comprises a unique combination of typesof information, as described herein. The types of information that maybe included in a synchronization signal block may comprise:

-   -   synchronization signals (primary synchronization signals (PSS),        secondary synchronization signals (SSS), and/or tertiary        synchronization signals (TSS))    -   one or more physical broadcast channels (PBCH)    -   first reference signals (e.g., the first reference signal(s)        used for a measurement)    -   second reference signals (e.g., the second reference signal(s)        for PBCH decoding)    -   signaling (DCI: Downlink Control Information) carried by        Physical Downlink Control Channel (PDCCH)    -   data carried by Physical Downlink Shared Channel (PDSCH)    -   data carried by Physical Random Access Channel (PRACH)    -   paging information

The multiplexing structure of the synchronization signal block(s) may befixed. For example, the fixed multiplexing structure of thesynchronization signal block(s) may be defined, in advance, by aspecification. For example, the multiplexing (e.g., the PSS (may bemapped to symbols 0-2), the SSS (may be mapped to symbols 3-5), the TSS(may be mapped to symbols 6-7), the PBCH (may be mapped to symbols8-10), the first reference signals (may be mapped to symbols 11), thesecond reference signals (may be mapped to 8-10), the signaling carriedby the PDCCH (may be mapped to 12-13), and/or the data carried by thePDSCH) of the synchronization signal block(s) may be defined as thefixed multiplexing structure. Moreover, one or more types of thesynchronization signal block(s) may be defined based on the fixedmultiplexing structure. For example, one or more information defined asthe fixed multiplexing structure may be not transmitted (e.g., notmapped, skipped). For example, the PBCH may be not transmitted, in acertain timing, in the synchronization signal block(s). Also, the PBCHand the second reference signal may be not transmitted, in a certaintiming, in the synchronization signal block(s). For example, only thePSS and the SSS may be transmitted, in a certain timing, in thesynchronization signal block(s). Also, only the PSS and the SSS and thePBCH may be transmitted, in a certain timing, in the synchronizationsignal block(s). The details of different types of the synchronizationblock(s) may be described below.

In the above regard, the tertiary synchronization signals (TSS) aresynchronization signals which are provided by the access node inaddition to the primary synchronization signal (PSS) and secondarysynchronization signal (SSS). Moreover, as noted above, it is possiblealso to have plural Physical Broadcast Channels, e.g., PBCH1 and PBCH2.

Table 1 below shows the differing types of the synchronization signalblock(s) that may be generated by synchronization signal block generator60, and particularly shows by the ♦ symbol the unique combination oftypes of information that may be included in each synchronization signalblock. As described above, the unique combination of types ofinformation (also, the ♦ symbol) may be defined, in advance, by aspecification. The number of types of synchronization signal blocks, andthe information types, of Table 1 are not exhaustive, but are only forsake of simplified example.

TABLE 1 SSB Type PSS SSS TSS PBCH1 PBCH2 1 ♦ ♦ ♦ ♦ ♦ 2 ♦ ♦ ♦ ♦ 3 ♦ ♦ ♦ 4♦ ♦ ♦ 5 ♦ ♦

Thus, as shown in Table 1, SSB type 1 (i.e., a type 1 of SSB) includesfive types of information: PSS, SSS, TSS, PBCH1, and PBCH2. FIG. 7A alsoillustrates SSB type 1, and shows that the entire resource allocationfor the synchronization signal block of SSB type 1 is utilized for acombination of PSS, SSS, TSS, PBCH1, and PBCH2. By contrast FIG. 7Bshows that the synchronization signal block of SSB type 2 (i.e., a type2 of SSB), while being of the same size as the synchronization signalblock of SSB type 1, includes content for only PSS, SSS, TSS, and PBCH1.As explained herein, from the perspective of the synchronization signalblock type 1, a field of the synchronization signal block of FIG. 7B isskipped or nonconforming with respect to PBCH2.

FIG. 8 shows example basic acts or steps that may be performed by theaccess node 22A of FIG. 5A. Act 8-1 comprises the access node usingprocessor circuitry generating plural types of synchronization signalblocks for at least partially interspersed transmission over a radiointerface, each type of the synchronization signal block comprising aunique combination of differing types of information. For example, thesynchronization signal block generator 60 of FIG. 5A may generate bothsynchronization signal blocks of SSB type 1 of FIG. 7A andsynchronization signal blocks of SSB type 2 of FIG. 7B. Act 8-2comprises the node transmitter circuitry 34 at least partiallyinterspersing transmission of the plural types of synchronization signalblocks over the radio interface to at least one wireless terminal.

The wireless terminal 26 of FIG. 5A comprises terminal receivercircuitry 46 and terminal processor 40. The terminal receiver circuitry46 receives, in at least partially interspersed manner, synchronizationsignal blocks of differing types over the radio interface from an accessnode. As explained above, each synchronization signal block typecomprises a unique combination of differing types of information. Theterminal processor 40 comprises synchronization signal block typedetector 70, which is configured determine to which of plural types ofsynchronization signal blocks a received synchronization signal blockbelongs.

FIG. 9 thus shows example basic acts or steps that may be performed bythe wireless terminal 26 of FIG. 5A. Act 9-1 receiving, in at leastpartially interspersed manner, synchronization signal blocks ofdiffering types over a radio interface from an access node. Act 9-2comprises the wireless terminal 26 using processor circuitry, e.g.,synchronization signal block type detector 70, to determine to which ofplural types of synchronization signal blocks a received synchronizationsignal block belongs.

It should be noted that, for a given carrier frequency band, thesynchronization signal blocks of all types have the same size (e.g.,same number of frame resources), and are essentially formatted orconfigured so that, from synchronization signal block type tosynchronization signal block type, the same resources are similarlypartitioned. For example, in size of the fields comprising thesynchronization signal blocks of FIG. 7A and FIG. 7B are of the samesize and are similarly situated within the synchronization signal block.

FIG. 5B illustrates an embodiment and mode of access node 22B in whichthe synchronization signal block generator 60B designates a first typeof synchronization signal block as a “standard” synchronization signalblock, and other types of synchronization signal blocks (e.g., a secondtype of synchronization signal block, and/or a third type ofsynchronization signal block) as “non-standard” synchronization signalblocks. Thus the synchronization signal block generator 60B of FIG. 5Bis shown as generating both standard and non-standard synchronizationsignal block types. Preferably the first or standard type ofsynchronization signal block contains information for a fixed number ofdifferent types of information and is considered a “full” or “complete”synchronization signal block (such as the synchronization signal blockof FIG. 7A). Namely, the first or standard type of synchronizationsignal block may contain full information (i.e., all information)defined as the fixed multiplexing structure. However, from theperspective of the type of the standard synchronization signal block, anon-standard type of synchronization signal block contains informationonly for a subset of the types of information included in the standardsynchronization signal block, as described above. For example, thesynchronization signal block of FIG. 7B includes only information forPSS, SSS, TSS, and PBCH (e.g., PBCH1) (but does not contain informationfor PBCH2, i.e., but does not contain other information included in thetype of the standard synchronization signal block).

Thus, from synchronization signal block type to synchronization signalblock type, for a non-standard synchronization signal block essentiallythe same resources (e.g., time resources and/or frequency resources) arepartitioned or allocated for the same types of information as in thestandard synchronization signal block, but only a subset of thoseresource allocations are used in the manner of the standardsynchronization signal block. The resources location allocations orpartitions are herein referred to as fields (or symbols (e.g., OFDMsymbols)). That is, in the standard synchronization signal block of FIG.7A there is a PSS field, a SSS field, a TSS field, a PBCH1 field, and aPBCH2 field. The non-standard synchronization signal block of FIG. 7Bhas the same fields, but the PBCH2 field is not filled with PBCH2information.

The synchronization signal block generator 60B of FIG. 5B generates astandard synchronization signal block which comprises a predeterminednumber of fields which respectively correspond to a predetermined numberof different types of information. For example, as described above, apredetermined number of fields which respectively correspond to apredetermined number of different types of information may be defined,in advance, by the specification. For example, the correspondence of theinformation type and the field is assigned (e.g., determined) by asynchronization signal block type definition, so that a standardsynchronization signal block type is expected to have field values thatare in conformance with the standard synchronization signal block typedefinition. That is, all of the fields of the standard synchronizationsignal block type are expected to have valid information according tothe type of information associated with the field by the synchronizationsignal block type definition. The definition of the particularsynchronization signal block type may be ascertained, for example, byreference to information such as Table 1.

The synchronization signal block generator 60B of FIG. 5B also generatesone or more non-standard synchronization signal block types. In thenon-standard synchronization signal block type only a subset of thefields include information in conformance with the standardsynchronization signal block type. That is, the type of informationincluded in one or more of the fields outside of the subset is not thetype of information anticipated or expected in accordance with thestandard synchronization signal block type definition. The fieldsoutside of the subset thus cannot be decoded in the manner of thestandard synchronization signal block type.

The wireless terminal of FIG. 5B receives and, using synchronizationsignal block type detector 70, decodes a synchronization signal block ofa standard synchronization signal block type that comprises apredetermined number of fields which respectively correspond to apredetermined number of different types of information in conformancewith the standard synchronization signal block type. Further, thewireless terminal of FIG. 5B also receives and (again usingsynchronization signal block type detector 70) decodes a non-standardsynchronization signal block type wherein only a subset of the fieldsinclude information in conformance with the standard synchronizationsignal block type.

For a non-standard synchronization signal block type, the fields outsideof the subset, i.e., the fields which do not include information inconformance with the standard synchronization signal block type andwhich cannot be decoded in the manner of the standard synchronizationsignal block type, may appear to be skipped or unused (e.g., theinformation is not transmitted) by the access node. In some exampleembodiments and modes such fields may in fact be un-used, or to containnull or empty or meaningless values. For example, the one or more fieldsof the type of the non-standard synchronization signal block may beassumed to be un-used (e.g., the information corresponding to the one ormore fields is not transmitted). Also, the one or more fields of thetype of the non-standard synchronization signal block may be assumed tocontain null, empty or meaningless values (e.g., all “0” or all “1”, forexample). Namely, the one or more fields set to null, empty ormeaningless values (e.g., all “0” or all “1”, for example) may becontained in the type of the non-standard synchronization signal block.But in other example embodiments and modes, such fields of thenon-standard synchronization signal block type may in advantageouslyutilized, as explained below. For example, the one or more fields of thetype of the non-standard synchronization signal block may be assumed tobe utilized as one or more fields of other information (e.g., one ormore fields of other information included in the type of thenon-standard synchronization signal). For example, as described below,the one or more fields of the type of the non-standard synchronizationsignal block may be assumed to be utilized for a repetition(s) of one ormore fields of other information

In the example access node 22C of FIG. 5C, node processor 30 includes asynchronization signal block generator 60C that repeats certain SSBinformation, already included in another field of the synchronizationsignal block, in the apparently skipped fields of a non-standardsynchronization signal block type. That is, the synchronization signalblock generator 60C of FIG. 5C includes, in one or more fields whichis/are outside of the subset of fields that conform to the standardsynchronization signal block type, repeated information which comprisesa repetition of information carried in a field of the subset. Forexample, if the synchronization signal block of FIG. 7A is considered asthe standard synchronization signal block and the synchronization signalblock of FIG. 7B is considered as a non-standard synchronization signalblock type relative to the synchronization signal block of FIG. 7A, FIG.7C shows that the synchronization signal block generator 60C of FIG. 5Chas generated a non-standard synchronization signal block type toinclude, in the field that otherwise would be allocated to the PBCH2(i.e., any information included in the type if the standardsynchronization signal block), information that essentially repeats thePSS. Information other than PSS information may be repeated, since therepetition of PSS is provide only as an example. In some exampleembodiments and modes, the synchronization signal block may be definedto include some or all information of a transmission channel, such asPDSCH, PDCCH, and/or PRACH, so the in the FIG. 5C example embodiment andmode the repeated information may, in some instances, be information ofa transmission channel.

In the example access node 22D of FIG. 5D, node processor 30 includes asynchronization signal block generator 60D that, in an apparentlyskipped one or more fields of a non-standard synchronization signalblock type, instead includes a signal or data not otherwise included ina field of the standard synchronization signal block type. Thus thesynchronization signal block generator 60D of FIG. 5D is shown as agenerator that includes signal and/or data, not otherwise alreadyincluded, in a synchronization signal block of a non-standardsynchronization signal block type. For example, if the synchronizationsignal block of FIG. 7A is considered as the standard synchronizationsignal block and the synchronization signal block of FIG. 7B isconsidered as a non-standard synchronization signal block type relativeto the synchronization signal block of FIG. 7A, FIG. 7D shows that thesynchronization signal block generator 60D of FIG. 5D has generated anon-standard synchronization signal block type to include, in the fieldthat otherwise would be allocated to the PBCH2, signal and/or datainformation that is not otherwise already included in thesynchronization signal block.

As examples, the signal and/or data information that may be included bythe synchronization signal block generator 60D of the access node ofFIG. 6D into the non-conforming fields of the non-standardsynchronization signal block type may comprise one or more of: (1) atleast partial content of a Physical Downlink Control Channel (PDCCH);(2) at least partial content of a Physical Downlink Shared Channel(PDSCH); and (3) at least partial content of a Physical Random AccessChannel (PRACH). For example, the one or more fields of the non-standardsynchronization signal may be assumed to be utilized as one or morefields of PDCCH, PDSCH, and/or PRACH. For example, the one or morefields of the non-standard synchronization signal may be assumed to beutilized as one or more fields of PSS, SSS, TSS, PBCH, the firstreference signals, and/or the second reference signals.

For the example embodiments and modes in which null or meaninglessinformation (e.g., all “0” or all “1”, for example) is included in thefields of a non-standard synchronization signal block type, the wirelessterminal 26 does not obtain useful information from those fields. But inthe situations in which meaningful information (repetitive SSBinformation in the case of FIG. 7C and non-SSB information in the caseof FIG. 7D) is included in those fields, the synchronization signalblock type detector 70 of the wireless terminal 26 is preconfigured toknow the significance of those fields and to obtain meaningfulinformation therefrom. For example, the resources used by skippedsignal/channel/signaling/data in one SS block may be used by othersignals/channels/signaling/data, e.g., in the format of repetition ofother signals/channels/signaling/data (in the manner of FIG. 7C); or inthe format of always being used by PDCCH, and/or PDSCH, and/or PRACH(i.e., other information) for transmission (in the manner of FIG. 7D).The wireless terminal 26 assumes one fixed predefined resource reuseformat for each SS block structure type, thereby enabling the wirelessterminal to obtain the further information from the non-standardsynchronization signal block type.

In the foregoing it has been assumed that the standard synchronizationsignal block type is type 1 of Table 1, and that an example of anon-standard synchronization signal block type is type 2 of Table 2. Itshould be understood, however, that such choices are merely for sake ofexample, and that the standard synchronization signal block type may beother than type 1 of Table 1, and the non-standard synchronizationsignal block type may be other than type 2. In this latter regard, the“non-conforming field” that is outside of the subset of fields thatconform to the standard synchronization signal block type may be otherthan the PBCH2. For example, Type 2 of Table 1 could be chosen as thestandard synchronization signal block type and type 3 could be chosen asa non-standard synchronization signal block type, with the result thatthe field of the non-standard synchronization signal block type thatcorresponds to the TSS field may either be null or (as in the case ofFIG. 7C) filled with repeating SSB information, or (as in the case ofFIG. 7D) be filled with non-SSB signaling and/or data information.

Further to the foregoing, in some example embodiments and modes thesynchronization signal block generator may process different frequencybands differently in terms of generation and transmission of the pluraltypes of synchronization signal blocks. For example, FIG. 5E shows anaccess node 22E in which the synchronization signal block generator 60Egenerates different synchronization signal block schemes for differentfrequency bands, each synchronization signal block scheme having adifferent set of differing synchronization signal block types.

For example, as shown in FIG. 11, synchronization signal block generator60E of access node 22E may generate a first set of differingsynchronization signal block types in a first frequency band, accordingto first SSB scheme 81, and also generate a second set ofsynchronization signal block types, according to a second SSB scheme 82,for a second frequency band. By way of example, the first frequency bandmay be frequencies of 6 GHz and above, in which synchronization signalblock generator 60E generate a first set of synchronization signalblocks to include synchronization signal block types 1, 2, and 4 (seeTable 1). But for the second frequency band of below 6 GHz, thesynchronization signal block generator 60E may generate a second set ofsynchronization signal block types to include synchronization signalblock types 2, 3, and 4. In the first set, synchronization signal blocktype 1 may be the standard synchronization signal block, while in thesecond set the synchronization signal block type 2 may be the standardsynchronization signal block. Table 2A and Table 2B illustrate the twodifferent synchronization signal block schemes for different frequencybands.

TABLE 2 SSB TYPES INCLUDED IN SCHEME 1 SSB Type PSS SSS TSS PBCH1 PBCH21 ♦ ♦ ♦ ♦ ♦ 2 ♦ ♦ ♦ ♦ 4 ♦ ♦ ♦

TABLE 3 SSB TYPES INCLUDED IN SCHEME 2 SSB Type PSS SSS TSS PBCH1 PBCH22 ♦ ♦ ♦ ♦ 3 ♦ ♦ ♦ 4 ♦ ♦ ♦

The choices of SSB types for inclusion in the schemes of Table 2 andTable 3 are merely for sake of example, other scheme configurations areencompassed hereby. Moreover, for the frequency band differentiation ofplural synchronization signal block types, it should be understood thatthe differentiation may occur with respect to more than two frequencybands and thus more than two schemes.

In some example embodiments and modes such as that of FIG. 5F, theaccess node may provide for each synchronization signal block anindication of its synchronization signal block type, and such indicationof synchronization signal block type may be detectable by a receivingwireless terminal. In other example embodiments and modes, the accessnode may not provide explicit identification of synchronization signalblock type, but may nevertheless intersperse synchronization signalblocks of differing synchronization signal block types in transmissionto a wireless terminal. In such non-identified mode, the wirelessterminal may initially assume that received synchronization signalblocks belong to a first or standard synchronization signal block type,but upon encountering a synchronization signal block that does notdecode according to the standard synchronization signal block type, thewireless terminal may have to deduce or otherwise determine the contentsof the received non-standard synchronization signal block.

FIG. 5F illustrates an example access node 22F which may, in accordancewith differing example embodiments and modes, provide identification ofsynchronization signal block type (SSB TYPE ID) in various ways. Forexample, the node processor of the access node 22F may providesynchronization signal block type identification using an index, or acombination of two or more indexes, which is/are mapped to thesynchronization signal block structure. A synchronization signal blocktype-indicating index may be of several types: synchronization signalblock index; synchronization signal burst index; synchronization signalburst set index. The concepts of synchronization signal block,synchronization signal block burst, and synchronization signal blockburst set are understood with reference to FIG. 3, for example. Thus,the indication of a synchronization signal block type may comprise oneor more of a synchronization signal block index, a synchronizationsignal block burst index, and a synchronization signal block burst setindex.

In some example embodiments and modes an “index” may be obtained fromone symbol, from a combination of symbols, or any other information orpattern of information carried in a frame. The index(es) may be includedin the synchronization signal block itself (as shown by way of examplein FIG. 10A) or carried elsewhere in the frame (as shown by way ofexample in FIG. 10B). For example, the index(es) may be carried in thetertiary synchronization signal (TSS) of a synchronization signal blockthat includes a tertiary synchronization signal (TSS).

In some example embodiments and modes an “index” may refer to a timeand/or frequency locator for the frame. For example, the wirelessterminal may identify the type of the synchronization signal block(e.g., SSB TYPE ID) based on the index (e.g., a time index, and/or afrequency index) of the synchronization signal block, the index(indices) of the synchronization signal burst, and/or the index of thesynchronization signal burst set. Namely, the index (indices) of thesynchronization signal block, the synchronization signal burst, and/orthe synchronization signal burst set may be used for the indication ofthe synchronization signal block type. See, for example, FIG. 10C whichshows how an index indicative of SSB type may be related to frequency(“frequency index”). Frequency index is defined as the offset of thefirst subcarrier of SSB in frequency domain to some common frequencyreference point.

In the above regard, for example, based on the index (indices) of thesynchronization signal block, the synchronization signal burst, and/orthe synchronization signal burst set, the wireless terminal may derive(identify, recognize), a symbol(s), and/or a slot index in a radioframe. For example, one index may be defined (e.g., indicated,configured) for every synchronization signal block within onesynchronization signal burst, and/or one synchronization signal burstset. Also, one index that is specific to each synchronization signalblock may be defined within one synchronization signal burst, and/or onesynchronization signal burst set. Also, one index of synchronizationsignal burst that is specific to each synchronization signal burst maybe defined within one synchronization signal burst set. Also, the index(indices) of synchronization signal burst, and/or synchronization signalburst set may be common across synchronization signal blocks in eachsynchronization signal burst, and/or each synchronization signal burstset.

Moreover, the index (indices) of the synchronization signal block may beindicated (identified, configured) by using PSS, SSS, TSS, and/or PBCH.For example, the index (indices) of the synchronization signal block maybe implicitly, and/or explicitly indicated by using PBCH. Also, thewireless terminal may assume a synchronization signal block (e.g., agiven synchronization signal block) is repeated with a periodicity ofsynchronization signal burst. Also, the wireless terminal may assume asynchronization signal block (e.g., a given synchronization signalblock) is repeated with a periodicity of synchronization signal burstset. Here, the periodicity of synchronization signal burst, and/or theperiodicity of synchronization signal burst set may be predefined with adefault fixed value, or may be configured by the access node (e.g., thebase station apparatus).

As a first example implementation of an index indication ofsynchronization signal block type, assume that an SS block index (i.e.,the index of SS block) starts from zero (0). In such case, an SS blockindex=0 may indicate the first type of SS block structure (which mayinclude complete set of synchronization signal block information or the“standard” synchronization signal block type discussed above); SS blockindex=1 may indicate a second type of SS block structure (which mayinclude one subset of the information defined for the first type of SSblock structure); SS block index=2 may indicate a third type of SS blockstructure (which may include another subset of the information definedfor the first type of SS block structure); and so on so forth. Thus, theaccess node of FIG. 5F may generate and transmit a synchronizationsignal block index to indicate the synchronization signal block type ofa synchronization signal block.

As a second example implementation of an index indication ofsynchronization signal block type, the access node 22F may provide a SSburst set index (i.e., the index of SS burst, and/or the index of SSburst set) which indicates the type of SS block structure. In providingthe SS burst set index for this second example implementation, all SSblocks in a particular SS burst set share the same SS block structure.In other words, in this second example implementation, an index of ahigher hierarchical layer (burst set) may subsume or encompass thebursts or synchronization signal blocks included in the higher layer.Thus, in accordance with this second example implementation, the accessnode may generate and transmit a synchronization signal burst index toindicate the synchronization signal block type of plural synchronizationsignal blocks belonging to a synchronization signal block burst, or maygenerate and transmit a synchronization signal burst set index toindicate the synchronization signal block type of plural synchronizationsignal blocks belonging to a set of synchronization signal block bursts.

As a third example implementation of an index indication ofsynchronization signal block type, a SS block odd index of SS burst setodd index indicates the first type of SS block structure, an SS blockodd index of SS burst set even index indicates the second type of SSblock structure, and so on so forth. Thus, it may also be that the useof two or more of the values of synchronization signal block index,synchronization signal block burst index, and synchronization signalblock burst set index serve as indices to a two or more dimensionalmapping to a particular synchronization signal block type value for aparticular synchronization signal block. For example, a combination oftwo or more of a synchronization signal block index, a synchronizationsignal block burst index, and a synchronization signal block burst setindex generated by the processor circuitry may be used to indicate thesynchronization signal block type.

The example access node 22F of FIG. 5F may provide identification ofsynchronization signal block type (SSB TYPE ID) in yet other ways. Forexample, the access node may include an indication of synchronizationsignal block type in the SSB itself, e.g., in a PBCH or in the primaryor secondary synchronization signal.

In some example embodiments and modes the access node is configured togenerate the synchronization signal block in a manner in which itssynchronization signal block type as ascertainable from a transmissionparameter. For example, in the example access node 22G of FIG. 5G thesynchronization signal block type is determined from a parameter knownas the system frame number (SFN), e.g., the SFN of a frame in which thesynchronization signal block is included. Namely, the synchronizationsignal block type may be determined based on the system frame number(SFN). As known in the art, the access node generates system framenumbers (SFN), which are typically expressed in a finite number of bits,e.g., ten bits. The finite number of bits means that the SFN numbers arere-used after the maximum SFN expressed by the finite number of bits isreached. For example, if the SFN has ten bits, then the SFNs areassigned as 0 through 1023, and thereafter repeated. So in the exampleembodiments and modes such as that typified by FIG. 5G that use SFN toidentify synchronization signal block type, the access node 22G isconfigured to associate a given synchronization signal block type withone or more certain SFN values and to include that given synchronizationsignal block type in the frame(s) having the associated SFN value. Thus,the synchronization signal block generator 60G generates a particularsynchronization signal block for inclusion in a system frame having asystem frame number (SFN) that is associated with a synchronizationsignal block type for the particular synchronization signal block.

In the example of FIG. 5G the wireless terminal 26 obtains asynchronization signal block type indication for a particularsynchronization signal block on a basis of a system frame number (SFN)of a system frame in which the particular synchronization signal blockis transmitted. In particular, the wireless terminal 26 obtains asynchronization signal block type indication for a particularsynchronization signal block on a basis of a system frame number (SFN)of a system frame in which the particular synchronization signal blockis transmitted.

As an example of the foregoing, the wireless terminal 26 may identifydifferent SS block structures through system frame numbers (SFN), whichcan be obtained from decoding PBCH, or at least partially from PBCH. Forexample, in some particular SFN, e.g., SFN=100, 220, 300 . . . , the SSblock structure with multiplexed data transmission is used.

In the above regard, FIG. 12 shows an example scenario in which a firstsynchronization signal block type (e.g., standard synchronization signalblock type) is associated with SFN=100, and a second synchronizationsignal block type (e.g., non-standard synchronization signal block type)is associated with SFN=500. When the wireless terminal 26 receives asynchronization signal block in a frame having SFN=100, the wirelessterminal 26 will know that the received synchronization signal block isof the first synchronization signal block type. Alternatively, when thewireless terminal 26 receives a synchronization signal block in a framehaving SFN=500, the wireless terminal 26 will know that the receivedsynchronization signal block is of the second synchronization signalblock type.

Other values of SFN may be associated with one or more synchronizationsignal block types. Moreover, a first synchronization signal block typemay be associate with plural SFNs, e.g., SFN=100, SFN=200, . . . ,SFN=400, and likewise the second synchronization signal block type maybe associated with plural SFNs (e.g., SFN=500, SFN=600, etc . . . ).

As a variation of FIG. 5G, the access node 22G may use a combination ofindex-explicit identification and SFN value to identify thesynchronization signal block type. For example, for some predefinedSFN(s), the SS block index X with SS burst index Y and with SS burstindex Z may indicate one particular type of SS block structure orsynchronization signal block type. For another predefined SFN(s), the SSblock index X with SS burst index Y and with SS burst index Z mayindicate another particular type of SS block structure, e.g., anothersynchronization signal block type.

Described above are various ways in which the access node may provide anindication of the synchronization signal block type for a particularsynchronization signal block. Among the ways above discussed areinclusion of one or more index(es) and generation of the synchronizationsignal block in association with a transmission parameter such as systemframe number (SFN). In some example embodiments and modes, the accessnode may further be configured to transmit synchronization signal blocktype override information that supersedes the above indications (e.g.,index or SFN association) of synchronization signal block type providedby the network. For example, when the wireless terminal 26 is in RadioResource Control (RRC) connected mode/state, the structure of detectedSS block (i.e., the synchronization signal block type) can be updated bydedicated RRC signaling, or broadcast signaling, for example. Then,after the wireless terminal 26 receives the updating signaling fromnetwork indicating its block structure, the indicated updating structureoverrides the wireless terminal's assumption of SS block structuremapped from index and/or SFN information. On the other hand, when thewireless terminal 26 is in inactive state or when the wireless terminal26 is in idle mode, the structure of detected SS block can be updated bybroadcast signaling.

In example embodiments and modes such as many of those described above,the wireless terminal 26 may be configured essentially to be pre-alertedor previously warned to be on the outlook for synchronization signalblocks of differing synchronization signal block types, and indeed inmany such example embodiments and modes the access node may provide thewireless terminal 26 with a mechanism for identifying thesynchronization signal block type of a received synchronization signalblock. But in other example embodiments and modes, such as thatillustrated in FIG. 5H, the wireless terminal 26 may nominally orblindly suppose that all incoming or received synchronization signalblocks are to be of a particular synchronization signal block type(e.g., the standard synchronization signal block type), and in such casemay have to react to receipt of a synchronization signal block of anon-standard synchronization signal block type. In FIG. 5H the terminalprocessor is shown as comprising synchronization signal block typedetector with candidate trial field decoding 70H. The synchronizationsignal block type detector with candidate trial field decoding 70H has alist of candidate information elements for trial, the candidate could bethe complete set or subset of information elements in the standard SSB.

Thus, as indicated above, in some example embodiments and modes, theaccess node may not provide explicit identification of synchronizationsignal block type, but may nevertheless intersperse synchronizationsignal blocks of differing synchronization signal block type intransmission to a wireless terminal. In such non-identified mode, thewireless terminal may initially assume that received synchronizationsignal blocks belong to a first or standard synchronization signal blocktype. But upon encountering a synchronization signal block that does notdecode according to the standard synchronization signal block type, thesynchronization signal block type detector with field decoding 70 of thewireless terminal of FIG. 5H may have to deduce or otherwise determinethe contents of the received non-standard synchronization signal block.For example, the synchronization signal block type detector withcandidate trial field decoding 70H may initially process the receivedsynchronization signal block as a standard synchronization signal blocktype, but upon encountering a field of the received synchronizationsignal block that does not decode according to the standardsynchronization signal block type, the synchronization signal block typedetector with candidate trial field decoding 70H may attempt todetermine an appropriate information type for the encountered field.

If, for example, upon entering a new cell (e.g., for initial cellselection, and/or for an idle wireless terminal), the wireless terminalreceives (assumes) a synchronization signal block that is of thestandard synchronization signal block type, the synchronization signalblock type detector with candidate trial field decoding 70H of thewireless terminal 26 can ascertain the structure of the synchronizationsignal block to obtain or confirm understanding of what resources of thesynchronization signal block are allocated to the information carried bythe primary synchronization signal block (e.g., the standardsynchronization signal block type). Based on the example and guidance ofsuch a first received synchronization signal block being a standardsynchronization signal block, the wireless terminal can intelligentlyattempt to similarly decode further synchronization signal blocksreceived over the air interface. As such, the wireless terminalpreliminarily assumes that the wireless terminal knows what type ofinformation will be allocated to each partition or segment (e.g., field)of the synchronization signal block, and accordingly engages anappropriate decoder/detector for each segment or partition. But shouldthe wireless terminal encounter a field of the received synchronizationsignal block that does not decode with the type of decoder that thewireless terminal believed to be appropriate for that field, e.g.,according to the CRC check of PBCH decoding, the negative result isshown in the field believed to be PBCH, then the wireless terminal willrealize that the received synchronization signal block is a non-standardsynchronization signal block type. Upon such realization of receipt of anon-standard synchronization signal block type, the synchronizationsignal block type detector with candidate trial field decoding 70H mayuse a trial and error approach to decode the non-conforming field,through confirmation with some criteria, e.g., CRC check. To this end,the wireless terminal 26 includes logic for sequentially implementingdifferent decoders/detectors according to possible differentsynchronization signal block field types, e.g. types of synchronizationsignal block information, until the wireless terminal is successful indecoding/detecting the non-conforming field.

On the other hand, if upon entering a new cell, the wireless terminalreceives (assumes) a synchronization signal block that is not of theprimary synchronization signal block type (e.g., the standardsynchronization signal block type), the wireless terminal may engagedecoders of different types, on a trial and error basis, in an attemptto deconstruct the received synchronization signal block. Namely, thewireless terminal receives (assumes) a synchronization signal block thatis any of the non-standard synchronization signal block type.

In some example embodiments and modes the synchronization signal blocktype detector with candidate trial field decoding 70H may attempt tosuccessfully decode/detect every field of a received synchronizationsignal block in order to consider the synchronization signal block asbeing fully processed. That is, the synchronization signal block typedetector with candidate trial field decoding 70H blindly decodes/detectsthe fields of the synchronization signal block until correct informationis obtained from each field of the synchronization signal block.

In other example embodiments and modes, less than full recovery of thesynchronization signal block may be useful or advantageous, particularlyif the wireless terminal 26 was expecting a synchronization signal blockto be of standard synchronization signal block type but discovers thatthe received synchronization signal block is not of the standardsynchronization signal block type. In example embodiments and modeshaving less than full recovery of a synchronization signal block, theinformation/fields included in a synchronization signal block may bedivided into at least two classes or categories: (1) a first class(which may be, for example) essential synchronization signal informationand (2) a second class (which may be, for example, non-essentialsynchronization signal information. In example embodiments and modes inwhich the first class comprises essential synchronization signalinformation, such essential synchronization information may comprise,for example, any one, or any combination of synchronization signalinformation elements which are generally included in standardsynchronization signal blocks, such as example PSS/SSS. In exampleembodiments and modes in which the first class comprises non-essentialsynchronization signal information, such essential synchronizationinformation may include fields of the synchronization signal block otherthan the fields of the essential synchronization signal information. Inthe example embodiments and modes having which less than full recoveryof a synchronization signal block, the synchronization signal block typedetector with candidate trial field decoding 70H may, upon encounteringa non-standard synchronization signal block type, perform modifiedsearch/decoding logic.

The modified search/decoding logic may be advantageous to help save timeand energy during SS block detection. For example, if in each SS blockthere is both first class information (e.g., essential information) andsecond class information (e.g., non-essential information), it may takea long time and considerable energy to do blind decoding to recoverfields of the block that are non-conforming to the standardsynchronization signal block type. Moreover, the SS block informationmay be repeated (like in LTE, PSS/SSS is repeated every 5 ms, while PBCHis repeated every 40 ms). Therefore, if the wireless terminal can alwaysget essential information from each SS block, then whether the wirelessterminal 26 needs to get non-essential information from each SS blockmay not be an issue.

An example of modified search/decoding logic is to search only searchonly one candidate in each field, e.g., search only one candidate whichis believed to be the appropriate one in that field in standard SSB. Ifsuch one search fails, the synchronization signal block type detectorwith candidate trial field decoding 70H thereafter just obtains theessential information from the synchronization signal block, and maylater attempt to obtain correct non-essential information from anotherSS block. Alternatively, as another example of modified search/decodinglogic, the wireless terminal 26 may decide that, after recovering thefirst class (e.g., essential SSB information), it may not be worthattempting to recover the second class information (e.g., thenon-essential information) from this particular synchronization signalblock, and thereby save energy that otherwise would be expended in atrial and error search for candidates for the field that does notconform to the standard synchronization signal block type.

Thus, in an example implementation that employs the modifiedsearch/decoding logic, the upon encountering the field of the receivedsynchronization signal block that does not decode according to thestandard synchronization signal block type, the synchronization signalblock type detector with candidate trial field decoding 70H may try onecandidate for the field and, if the one candidate is not successful forthe field, may use only synchronization signal information thatotherwise is recoverable from the non-standard synchronization signalblock.

In an example embodiment and mode, in processing a series ofsynchronization signal blocks the wireless terminal may use acombination of index indication of synchronization signal block type (todetermine the synchronization signal block type of some of thesynchronization signal blocks of the series) and the wireless terminal'sown decoding to determine the synchronization signal block types ofother synchronization signal blocks of the series. For example, thesynchronization signal block type detector 70 may start to process oneor more synchronization signal blocks of a series of synchronizationsignal blocks using the indication of synchronization signal block typeas provided by the access node, but thereafter may switch over to usingits synchronization signal block type detector with candidate trialfield decoding 70H, as described above.

Use of Beam ID to Determine Synchronization Signal Block Time Index

In another example embodiment and mode, the synchronization signalblocks generated by the access node 22 are beam-based. FIG. 13 showssynchronization signal block burst set 80, comprising synchronizationsignal block bursts 82 ₁ and 82 ₂. Each synchronization signal blockburst 82 comprises plural synchronization signal blocks, each of thesynchronization signal blocks having a different synchronization signalblock time index. Each of the synchronization signal blocks, and thuseach of the synchronization signal block time indexes associated withthe respective synchronization signal blocks, is paired or associatedwith a unique one of plural beams transmitted by the access node.

FIG. 5I shows access node 22F as comprising a system information (SI)generator 54 which generates an identity that expresses, e.g., beam ID(beam identifier (BID). FIG. 5I further shows that the terminalprocessor 40 of wireless terminal 26I comprises a synchronization signalblock detector 88 that determines a synchronization signal block timeindex from the beam ID that is received from the access node 26I.

FIG. 14 shows example, basic acts or steps performed by the wirelessterminal 26I of FIG. 5I. Act 14-1 comprises the wireless terminalreceiving a beam identifier (BID) over radio interface 24 from accessnode 22F. The beam ID (beam identifier (BID) may be obtained in any ofthe manners described in U.S. provisional Patent application 62/453,986,filed Feb. 2, 2017, entitled “SYNCHRONIZATION SIGNAL TRANSMISSION ANDRECEPTION FOR RADIO SYSTEM”, which is incorporated herein by referencein its entirety. After the wireless terminal 26I has determined the beamidentifier (BID) by such techniques, as act 14-2 the synchronizationsignal block detector 88 uses the beam identifier (BID) to derive asynchronization signal block time index for a synchronization signalblock that is associated with the beam identifier (BID). For example,the beam identifier (BID) may be equated to the synchronization signalblock time index, or mathematically used to derive the synchronizationsignal block time index, or used as an index into a mapping table or thelike to ascertain the synchronization signal block time index. Further,as optional act 14-3, the terminal processor 40 may use thesynchronization signal block time index to determine a synchronizationsignal block type for a received synchronization signal block.

There may be two alternative example embodiments and modes for SS-blockindex. In a first example embodiment and mode, time index may be countedwithin one SS burst set (in which case, no SS burst concept is defined).In a second example embodiment and mode, the time index may be countedwithin SS burst. As used herein, beam identifier (BID) may be accordingto either of these alternative example embodiments and modes, e.g., beamID allocation (from network side) is either per SS burst, or per SSburst set.

Certain units and functionalities of node 22 and wireless terminal 26are, in example embodiments, implemented by electronic machinery,computer, and/or circuitry. For example, the node processors 30 andterminal processors 40 of the example embodiments herein describedand/or encompassed may be comprised by the computer circuitry of FIG.15. FIG. 15 shows an example of such electronic machinery or circuitry,whether node or terminal, as comprising one or more processor(s)circuits 90, program instruction memory 91; other memory 92 (e.g., RAM,cache, etc.); input/output interfaces 93; peripheral interfaces 94;support circuits 95; and busses 96 for communication between theaforementioned units.

The program instruction memory 91 may comprise coded instructions which,when executed by the processor(s), perform acts including but notlimited to those described herein. Thus is understood that each of nodeprocessor 30 and terminal processor 40, for example, comprise memory inwhich non-transient instructions are stored for execution.

In the above regard, the access node 22 of any of the exampleembodiments and modes described herein may comprise at least oneprocessor (e.g., processor 30/90); at least one memory (e.g., memory 91)including computer program code, the memory and the computer programcode configured to, working with the at least one processor, to causethe access node to perform the acts described herein, such as the actsof FIG. 8, for example. Similarly the wireless terminal 26 of any of theexample embodiments and modes described herein may comprise at least oneprocessor (e.g., processor 40/90); at least one memory (e.g., memory 91)including computer program code, the memory and the computer programcode configured to, working with the at least one processor, to causethe wireless terminal 26 to perform the acts described herein, such asthe acts of FIG. 9, for example.

The memory, or computer-readable medium, may be one or more of readilyavailable memory such as random access memory (RAM), read only memory(ROM), floppy disk, hard disk, flash memory or any other form of digitalstorage, local or remote, and is preferably of non-volatile nature. Thesupport circuits 95 may be coupled to the processors 90 for supportingthe processor in a conventional manner. These circuits include cache,power supplies, clock circuits, input/output circuitry and subsystems,and the like.

To summarize and expound upon the foregoing, a SS block structure hasbeen defined herein: the SS block may comprise synchronization signals(NR-PSS, and/or NR-SSS, and/or third synchronization signal (NR-TSS)indicating other information such as SS block index, and/or some othertype of SS), and/or NR-PBCH (one NR-PBCH, or two NR-PBCHs includingfirst physical broadcast channel and secondary physical broadcastchannel), and/or reference signals (e.g., Measurement RS (NR-MRS),and/or reference signals for PBCH decoding, and/or some other type ofRS), and/or signalling carried by NR-PDCCH, and/or data by NR-PDSCHand/or PRACH.

Further, the SS block may have fixed multiplexing structure for a givencarrier frequency band. For different carrier frequency bands (Oneexample is below 6 GHz and above 6 GHz. Of course, there could be morethan the above two carrier frequency band categories; the separationpoint(s) to categorize different carrier frequency band could also beother frequency(ies)), SS block may have different fixed structure.

Moreover, the fixed structure of SS block means for a given frequencyband, an SS block corresponds to N OFDM symbols based on the defaultsubcarrier spacing, and N is a constant. Moreover, the signal (asmentioned above concerning SS block structure) multiplexing structure isfixed as well. In other words, within the time and frequency resourcesdefined for an SS block, fixed time and frequency resources areallocated to corresponding signals/channels/signaling/data.

There are two alternative fixed multiplexing designs for SS block,referred to as Alt A and Alt B below.

For Alt A: There are M types SS block structures (where, M≥1) for agiven carrier frequency band. Each type of SS blocks has the same fixedmultiplexing structure.

Alt A.1: The UE identifies different SS block structure through index,e.g., SS block index, and/or SS burst index, and/or SS burst set index;in other words, any single one, or any combination of two, or thecombination of three types of index (SS block index, SS burst index, andSS burst set index) is mapped to one SS block structure. Therelationship could be any mapping from X index or index combinations toM (where, X≥1). (We might have a mapping figure here).

Example A.1.1: SS block index 0 (if SS block index starts from 0)indicates the first type of SS block structure (which may includecomplete set of information defined in paragraph 1); SS block index 1indicates the second type of SS block structure (which may include onesubset of the information defined for the first type of SS blockstructure. For example, the complete set of information consists ofPSS/SSS, reference signals and PBCH; this type of SS block structureconsists of PSS/SSS only); SS block index 2 indicates the third type ofSS block structure (which may include another subset of the informationdefined for the first type of SS block structure); and so on so forth.

Example A.1.2: Similarly, SS burst set index indicates the type of SSblock structure. It means all SS blocks in a particular SS burst setshares the same SS block structure.

Example A.1.3: SS block odd index of SS burst set odd index indicatesthe first type of SS block structure. SS block odd index of SS burst seteven index indicates the second type of SS block structure. And so on soforth.

Alt A.2: The UE identifies different SS block structure through systemframe number (SFN), which can be obtained from decoding PBCH, or atleast partially from PBCH. For example, in some particular SFN, e.g.,SFN=100, 200, 300 . . . , the SS block structure with multiplexed datatransmission is used. Of course, here we use “100, 200, 300” as anexample, they could be any other SFN numbers.

Alt A.3: Any combination of Alt A.1 and Alt A.2. For example, in somepredefined SFN(s), the SS block index X with SS burst index Y with SSburst index Z indicates one particular type of SS block structure.

Alt A.4: Information carried by PBCH directly to indicate SS blockstructure

Alt A.5: Information carried by SS directly to indicate SS blockstructure

From UE's perspective, the UE assumes one fixed mapping relationshipdefined in above Alt A.1 to Alt A.3. Once the UE obtains the indexand/or SFN information, the UE knows the structure of the SS block. Orthe UE obtains SS block structure information from decoded PBCHinformation or detected SS information, as described in Alt A.4 and AltA.5.

For the SS block structure without complete set of information (someinformation is skipped in the fixed multiplexing structure), there aretwo alternative designs, i.e., Alt A.X and Alt A.Y.

Alt A.X: The resources used by skipped signal/channel/signaling/data inone SS block are kept there without other use. So the UE doesn't getuseful information from the reserved resources (The reserved resourcesare filled with all “0” or all “1”).

Alt A.Y: As indicated in SLA 3707P, the resources used by skippedsignal/channel/signaling/data in one SS block are used by othersignals/channels/signaling/data, e.g., in the format of repetition ofother signals/channels/signaling/data; or in the format of always beingused by PDCCH, and/or PDSCH, and/or PRACH for transmission. The UEassumes one fixed predefined resource reuse format, as indicated in thisparagraph, for each SS block structure type. So the UE can get furtherinformation from this SS block.

In case of Alt A.Y, when the UE is in RRC connected mode/state, thestructure of detected SS block can be updated by dedicated RRCsignaling, or broadcast signaling; for example, once the UE receivessignaling from network indicating its block structure, the indicatedstructure overrides UE's assumption of SS block structure mapped fromindex and/or SFN information; on the other hand, when the UE is ininactive state or when the UE is in idle mode, the structure of detectedSS block can also be updated by broadcast signaling.

Alt B: All SS blocks have the same fixed multiplexing structure for agiven carrier frequency band. In this alternative, some information,which could be any one or more than one signals/channels/signaling/datadefined in the first paragraph, can be skipped in some SS blocks.However, the UE doesn't know which information is skipped. UE alwaysassumes the sole fixed multiplexing structure for SS block. For the SSblock structure without complete set of information (some information isskipped in the fixed multiplexing structure), the two alternativedesigns Alt A.X and Alt A.Y are also applicable to Alt B. The UE blindlydetects the SS block structure. In this design, the UE assumesperiodicity of each signal/channel/signaling/data in the SS block, e.g.,SS has periodicity of 5 ms; PBCH has periodicity of 40 ms; signaling isallowed to be transmitted in every 5 SS blocks; and data is allowed tobe transmitted in every 10 SS blocks; then once the UE successfullyblindly detects some information in some SS block, it knows in which SSblocks it detects the corresponding information again (in other words,it means the UE assumes different detection window including differentnumber of SS blocks to detect different signal/channel/signaling/data).Of course, the periodicity mentioned in the example could be any othervalues, and the information to construct SS block could also be any fromparagraph 1. If Alt A.X is adopted, the blind detection complexity islower, as it's easy for the UE to detect the reserved bits (The valuesof reserved bits are known to the UE, either all “0” or all “1”).

Similar as Alt A, the SS structure information can be updated by networksignaling according to UE's state.

Further, Alt B can also be combined with Alt A. For example, the UE candetect the SS block structure with method indicated in Alt A, e.g.,through SS block index information; then the UE can use Alt B tocontinue detecting signal/channel/signaling/data information in thefollowing SS block, e.g., through assumption ofsignal/channel/signaling/data periodicity information.

The technology disclosed herein thus comprises and encompasses thefollowing non-exhaustive example embodiments and modes:

Example Embodiment 1

An access node comprising:

processor circuitry configured to generate plural types ofsynchronization signal blocks for at least partially interspersedtransmission over a radio interface, each synchronization signal blocktype comprising a unique combination of differing types of information;

transmitter circuitry configured to at least partially interspersetransmission of the plural types of synchronization signal blocks overthe radio interface to at least one wireless terminal.

Example Embodiment 2

The access node of example embodiment 1, wherein the types ofinformation that are carried in one or more types of synchronizationsignal block types comprises three or more of the following:

a primary synchronization signal (PSS),

a secondary synchronization signal (SSS),

a tertiary synchronization signals (TSS));

one or more physical broadcast channels (PBCH);

a reference signal;

a reference signal for PBCH decoding

signaling carried by a Physical Downlink Control Channel (PDCCH);

data carried by a Physical Downlink Shared Channel (PDSCH); and

data carried by a Physical Random Access Channel (PRACH).

Example Embodiment 3

The access node of example embodiment 1, wherein the processor circuitryis configured:

to generate a synchronization signal block of a standard synchronizationsignal block type that comprises a predetermined number of fields whichrespectively correspond to a predetermined number of different types ofinformation in conformance with the standard synchronization signalblock type; and

to generate a non-standard synchronization signal block type whereinonly a subset of the fields include information in conformance with thestandard synchronization signal block type.

Example Embodiment 4

The access node of example embodiment 3, wherein the processor circuitryis configured to include null information in fields of the non-standardsynchronization signal block type which are outside of the subset.

Example Embodiment 5

The access node of example embodiment 3, wherein the processor circuitryis configured to include, in a field of the non-standard synchronizationsignal block type which is outside of the subset, repeated informationwhich comprises a repetition of information carried in a field of thesubset.

Example Embodiment 6

The access node of example embodiment 3, wherein the processor circuitryis configured to include, in a field of the non-standard synchronizationsignal block type which is outside of the subset, a signal or data nototherwise included in a field of the subset.

Example Embodiment 7

The access node of example embodiment 6, wherein the processor circuitryis configured to include, in the field of the non-standardsynchronization signal block type which is outside of the subset, one ormore of: (1) at least partial content of a Physical Downlink ControlChannel (PDCCH); (2) at least partial content of a Physical DownlinkShared Channel (PDSCH); and (3) at least partial content of a PhysicalRandom Access Channel (PRACH).

Example Embodiment 8

The access node of example embodiment 1, wherein the processor circuitryis configured to generate different synchronization signal block schemesfor different frequency bands, each synchronization signal block schemehaving a different set of differing synchronization signal block types.

Example Embodiment 9

The access node of example embodiment 8, wherein the processor circuitryis configured:

to generate a first set of differing synchronization signal block typesin a first frequency band; and

to generate a second set of synchronization signal block types for asecond frequency band.

Example Embodiment 10

The access node of example embodiment 1, wherein the processor circuitryis further configured to generate, for each synchronization signalblock, an indication of its synchronization signal block type, such thatthe indication of synchronization signal block type is detectable by areceiving wireless terminal.

Example Embodiment 11

The access node of example embodiment 1, wherein the indication of itssynchronization signal block type comprises one or more of asynchronization signal block index, a synchronization signal block burstindex, and a synchronization signal block burst set index.

Example Embodiment 12

The access node of example embodiment 1, wherein a combination of two ormore of a synchronization signal block index, a synchronization signalblock burst index, and a synchronization signal block burst set indexgenerated by the processor circuitry are used to indicate thesynchronization signal block type.

Example Embodiment 13

The access node of example embodiment 10, wherein the indication of thesynchronization signal block type is included in a Physical BroadcastChannel (PBCH).

Example Embodiment 14

The access node of example embodiment 10, wherein the indication of thesynchronization signal block type is included in the synchronizationsignal block.

Example Embodiment 15

The access node of example embodiment 10, wherein the processorcircuitry is further configured to transmit synchronization signal blocktype override information that supersedes another indication ofsynchronization signal block type provided by the access node.

Example Embodiment 16

The access node of example embodiment 1, wherein the processor circuitryis further configured to generate the synchronization signal block in amanner in which its synchronization signal block type as ascertainablefrom a transmission parameter.

Example Embodiment 17

The access node of example embodiment 16, wherein the processorcircuitry is further configured to generate a particular synchronizationsignal block for inclusion in a system frame having a system framenumber (SFN) that is associated with a synchronization signal block typefor the particular synchronization signal block.

Example Embodiment 18

The access node of example embodiment 1, wherein the processor circuitryis further configured to generate the synchronization signal block in amanner in which its synchronization signal block type as ascertainablefrom a combination of a transmission parameter and an indicatorgenerated and transmitted by the access node.

Example Embodiment 19

A method in an access node comprising:

using processor circuitry to generate plural types of synchronizationsignal blocks for at least partially interspersed transmission over aradio interface, each synchronization signal block type comprising aunique combination of differing types of information;

at least partially intersperse transmission of the plural types ofsynchronization signal blocks over the radio interface to at least onewireless terminal.

Example Embodiment 20

The method of example embodiment 19, further comprising:

using the processor circuitry to generate a synchronization signal blockof a standard synchronization signal block type that comprises apredetermined number of fields which respectively correspond to apredetermined number of different types of information in conformancewith the standard synchronization signal block type; and

using the processor circuitry to generate to generate a non-standardsynchronization signal block type wherein only a subset of the fieldsinclude information in conformance with the standard synchronizationsignal block type.

Example Embodiment 21

A wireless terminal comprising:

receiver circuitry configured to receive, in at least partiallyinterspersed manner, synchronization signal blocks of differing typesover a radio interface from an access node, each synchronization signalblock type comprising a unique combination of differing types ofinformation;

processor circuitry configured determine to which of plural types ofsynchronization signal blocks a received synchronization signal blockbelongs.

Example Embodiment 22

The wireless terminal of example embodiment 21, wherein the types ofinformation that are carried in one or more types of synchronizationsignal block types comprises three or more of the following:

a primary synchronization signal (PSS),

a secondary synchronization signal (SSS),

a tertiary synchronization signals (TSS));

one or more physical broadcast channels (PBCH);

a reference signal;

a reference signal for PBCH decoding

signaling carried by a Physical Downlink Control Channel (PDCCH);

data carried by a Physical Downlink Shared Channel (PDSCH); and

data carried by a Physical Random Access Channel (PRACH).

Example Embodiment 23

The wireless terminal of example embodiment 21, wherein the receivercircuitry is configured to receive:

a synchronization signal block of a standard synchronization signalblock type that comprises a predetermined number of fields whichrespectively correspond to a predetermined number of different types ofinformation in conformance with the standard synchronization signalblock type; and

a non-standard synchronization signal block type wherein only a subsetof the fields include information in conformance with the standardsynchronization signal block type.

Example Embodiment 24

The wireless terminal of example embodiment 23, wherein the processorcircuitry is configured to determine that null information exists infields of the non-standard synchronization signal block type which areoutside of the subset.

Example Embodiment 25

The wireless terminal of example embodiment 23, wherein the processorcircuitry is configured to obtain, from a field of the non-standardsynchronization signal block type which is outside of the subset,repeated information which comprises a repetition of information carriedin a field of the subset.

Example Embodiment 26

The wireless terminal of example embodiment 23, wherein the processorcircuitry is configured to obtain, from a field of the non-standardsynchronization signal block type which is outside of the subset, asignal or data not otherwise included in a field of the subset.

Example Embodiment 27

The wireless terminal of example embodiment 26, wherein the processorcircuitry is configured to obtain, from the field of the non-standardsynchronization signal block type which is outside of the subset, one ormore of: (1) at least partial content of a Physical Downlink ControlChannel (PDCCH); (2) at least partial content of a Physical DownlinkShared Channel (PDSCH); and (3) at least partial content of a PhysicalRandom Access Channel (PRACH).

Example Embodiment 28

The wireless terminal of example embodiment 21, wherein the receivercircuitry is configured to receive different synchronization signalblock schemes for different frequency bands, each synchronization signalblock scheme having a different set of differing synchronization signalblock types.

Example Embodiment 29

The wireless terminal of example embodiment 28, wherein the processorcircuitry is configured:

to obtain a first set of differing synchronization signal block types ina first frequency band; and

to obtain a second set of synchronization signal block types for asecond frequency band.

Example Embodiment 30

The wireless terminal of example embodiment 21, wherein the processorcircuitry is further configured to obtain from the access node, for eachsynchronization signal block, an indication of its synchronizationsignal block type.

Example Embodiment 31

The wireless terminal of example embodiment 21, wherein the indicationof its synchronization signal block type comprises one or more of asynchronization signal block index, a synchronization signal block burstindex, and a synchronization signal block burst set index.

Example Embodiment 32

The wireless terminal of example embodiment 21, wherein the processorcircuitry is configured to use a combination of two or more of asynchronization signal block index, a synchronization signal block burstindex, and a synchronization signal block burst set index to obtain thesynchronization signal block type.

Example Embodiment 33

The wireless terminal of example embodiment 30, wherein the indicationof the synchronization signal block type is obtained from a PhysicalBroadcast Channel (PBCH).

Example Embodiment 34

The wireless terminal of example embodiment 30, wherein the indicationof the synchronization signal block type is obtained from thesynchronization signal block.

Example Embodiment 35

The wireless terminal of example embodiment 30, wherein the receivercircuitry is further configured to receive synchronization signal blocktype override information that supersedes another indication ofsynchronization signal block type provided by the access node to thewireless terminal.

Example Embodiment 36

The wireless terminal of example embodiment 21, wherein the processorcircuitry is further configured to obtain a synchronization signal blocktype indication for a particular synchronization signal block on a basisof a system frame number (SFN) of a system frame in which the particularsynchronization signal block is transmitted.

Example Embodiment 37

The access node of example embodiment 21, wherein the processorcircuitry is further configured to obtain an indication of thesynchronization signal block type of a particular synchronization signalblock based on a combination of an indicator generated and transmittedby the access node and a system frame number (SFN) of a system frame inwhich the particular synchronization signal block is transmitted.

Example Embodiment 38

The wireless terminal of example embodiment 21, wherein processorcircuitry initially processes the received synchronization signal blockas a standard synchronization signal block type, but upon encountering afield of the received synchronization signal block that does not decodeaccording to the standard synchronization signal block type, attempts todetermine an appropriate information type for the encountered field.

Example Embodiment 39

The wireless terminal of example embodiment 38, wherein uponencountering the field of the received synchronization signal block thatdoes not decode according to the standard synchronization signal blocktype, the processor circuitry is configured to try one candidate for thefield and, if the one candidate is not successful for the field, usesonly synchronization signal information that otherwise is recoverablefrom the non-standard synchronization signal block.

Example Embodiment 40

The wireless terminal of example embodiment 21, wherein:

the receiver circuitry is further configured to receive a beamidentifier over a radio interface from an access node;

the processor circuitry is configured to use the beam identifier todetermine a synchronization signal block time index for asynchronization signal block that is associated with the beamidentifier.

Example Embodiment 41

The wireless terminal of example embodiment 40, wherein the processorcircuitry is configured to use the beam identifier in a mappingoperation to ascertain the synchronization signal block time index.

Example Embodiment 42

A method in a wireless terminal comprising:

receiving, in at least partially interspersed manner, synchronizationsignal blocks of differing types over a radio interface from an accessnode, each synchronization signal block type comprising a uniquecombination of differing types of information;

using processor circuitry to determine to which of plural types ofsynchronization signal blocks a received synchronization signal blockbelongs.

Example Embodiment 43

The method of example embodiment 42, further comprising:

receiving and decoding a synchronization signal block of a standardsynchronization signal block type that comprises a predetermined numberof fields which respectively correspond to a predetermined number ofdifferent types of information in conformance with the standardsynchronization signal block type; and

receiving and decoding a non-standard synchronization signal block typewherein only a subset of the fields include information in conformancewith the standard synchronization signal block type.

Example Embodiment 44

The method of example embodiment 42, further comprising the processorcircuitry initially processing the received synchronization signal blockas a standard synchronization signal block type, but upon encountering afield of the received synchronization signal block that does not decodeaccording to the standard synchronization signal block type, attemptingto determine an appropriate information type for the encountered field.

Example Embodiment 45

The method of example embodiment 38, further comprising uponencountering the field of the received synchronization signal block thatdoes not decode according to the standard synchronization signal blocktype, the processor circuitry trying one candidate for the field and, ifthe one candidate is not successful for the field, using onlysynchronization signal information that otherwise is recoverable fromthe non-standard synchronization signal block.

Example Embodiment 46

The method of example embodiment 21, further comprising:

receiving a beam identifier over a radio interface from an access node;

the processor circuitry using the beam identifier to determine asynchronization signal block time index for a synchronization signalblock that is associated with the beam identifier (BID).

Example Embodiment 47

The method of example embodiment 46, further comprising the processorcircuitry using the synchronization signal block time index to determinethe synchronization signal block type for a received synchronizationsignal block.

Example Embodiment 48

A user equipment comprising:

receiving circuitry configured to receive, from a base stationapparatus, a radio resource control signaling including information, theinformation being used for indicating whether a primary synchronizationsignal and a secondary synchronization signal and a physical broadcastchannel and a reference signal for decoding the physical broadcastchannel are transmitted in a block consisting of a constant number ofOFDM symbols, wherein the receiving circuitry is configured to receive,based on the information, from the base station apparatus, the block inwhich the primary synchronization signal and the secondarysynchronization signal and the physical broadcast channel and thereference signal for decoding the physical broadcast channel aretransmitted,

the primary synchronization signal and the secondary synchronizationsignal are used for identifying a physical cell identity, and

the physical broadcast channel is used for carrying System Frame Numberinformation.

Example Embodiment 49

The user equipment of Example Embodiment 48: further comprisingprocessing circuitry configured to:

obtain the physical cell identity from the primary synchronizationsignal and the secondary synchronization signal;

obtain the System Frame Number information from the physical broadcastchannel.

Example Embodiment 50

A base station apparatus comprising:

transmitting circuitry configured to transmit, to a user equipment, aradio resource control signaling including information, the informationbeing used for indicating whether a primary synchronization signal and asecondary synchronization signal and a physical broadcast channel and areference signal for decoding the physical broadcast channel are mappedto a block consisting of a constant number of OFDM symbols, wherein

the transmitting circuitry is configured to transmit, based on theinformation, to the user equipment, the block to which the primarysynchronization signal and the secondary synchronization signal and thephysical broadcast channel and the reference signal for decoding thephysical broadcast channel are mapped,

the primary synchronization signal and the secondary synchronizationsignal are used for identifying a physical cell identity, and

the physical broadcast channel is used for carrying System Frame Numberinformation.

Example Embodiment 50

The base station of Example Embodiment 50, further comprising processingcircuitry configured to:

express the physical cell identity using the primary synchronizationsignal and the secondary synchronization signal;

express the System Frame Number information using the physical broadcastchannel

Example Embodiment 52

A communication method of a user equipment comprising:

receiving, from a base station apparatus, a radio resource controlsignaling including information, the information being used forindicating whether a primary synchronization signal and a secondarysynchronization signal and a physical broadcast channel and a referencesignal for decoding the physical broadcast channel are transmitted in ablock consisting of a constant number of OFDM symbols, and

receiving, based on the information, from the base station apparatus,the block in which the primary synchronization signal and the secondarysynchronization signal and the physical broadcast channel and thereference signal for decoding the physical broadcast channel aretransmitted, wherein

the primary synchronization signal and the secondary synchronizationsignal are used for identifying a physical cell identity, and

the physical broadcast channel is used for carrying System Frame Numberinformation.

Example Embodiment 53

The method of Example Embodiment 52, further comprising using processingcircuitry to:

obtain the physical cell identity from the primary synchronizationsignal and the secondary synchronization signal;

obtain the System Frame Number information from the physical broadcastchannel.

Example Embodiment 54

A communication method of a base station apparatus comprising:

transmitting, to a user equipment, a radio resource control signalingincluding information, the information being used for indicating whethera primary synchronization signal and a secondary synchronization signaland a physical broadcast channel and a reference signal for decoding thephysical broadcast channel are mapped to a block consisting of aconstant number of OFDM symbols, and

transmitting, based on the information, to the user equipment, the blockto which the primary synchronization signal and the secondarysynchronization signal and the physical broadcast channel and thereference signal for decoding the physical broadcast channel are mapped,wherein

the primary synchronization signal and the secondary synchronizationsignal are used for identifying a physical cell identity, and

the physical broadcast channel is used for carrying System Frame Numberinformation.

Example Embodiment 55

The method of Example Embodiment 54, further comprising using processingcircuitry to:

express the physical cell identity using the primary synchronizationsignal and the secondary synchronization signal;

express the System Frame Number information using the physical broadcastchannel

Although the processes and methods of the disclosed embodiments may bediscussed as being implemented as a software routine, some of the methodsteps that are disclosed therein may be performed in hardware as well asby a processor running software. As such, the embodiments may beimplemented in software as executed upon a computer system, in hardwareas an application specific integrated circuit or other type of hardwareimplementation, or a combination of software and hardware. The softwareroutines of the disclosed embodiments are capable of being executed onany computer operating system, and is capable of being performed usingany CPU architecture. The instructions of such software are stored onnon-transient computer readable media.

The functions of the various elements including functional blocks,including but not limited to those labeled or described as “computer”,“processor” or “controller”, may be provided through the use of hardwaresuch as circuit hardware and/or hardware capable of executing softwarein the form of coded instructions stored on computer readable medium.Thus, such functions and illustrated functional blocks are to beunderstood as being either hardware-implemented and/orcomputer-implemented, and thus machine-implemented.

In terms of hardware implementation, the functional blocks may includeor encompass, without limitation, digital signal processor (DSP)hardware, reduced instruction set processor, hardware (e.g., digital oranalog) circuitry including but not limited to application specificintegrated circuit(s) [ASIC], and/or field programmable gate array(s)(FPGA(s)), and (where appropriate) state machines capable of performingsuch functions.

In terms of computer implementation, a computer is generally understoodto comprise one or more processors or one or more controllers, and theterms computer and processor and controller may be employedinterchangeably herein. When provided by a computer or processor orcontroller, the functions may be provided by a single dedicated computeror processor or controller, by a single shared computer or processor orcontroller, or by a plurality of individual computers or processors orcontrollers, some of which may be shared or distributed. Moreover, useof the term “processor” or “controller” shall also be construed to referto other hardware capable of performing such functions and/or executingsoftware, such as the example hardware recited above.

The functions of the various elements including functional blocks,including but not limited to those labeled or described as “computer”,“processor” or “controller”, may be provided through the use of hardwaresuch as circuit hardware and/or hardware capable of executing softwarein the form of coded instructions stored on computer readable medium.Thus, such functions and illustrated functional blocks are to beunderstood as being either hardware-implemented and/orcomputer-implemented, and thus machine-implemented.

Nodes that communicate using the air interface also have suitable radiocommunications circuitry. Moreover, the technology can additionally beconsidered to be embodied entirely within any form of computer-readablememory, such as solid-state memory, magnetic disk, or optical diskcontaining an appropriate set of computer instructions that would causea processor to carry out the techniques described herein.

It will be appreciated that the technology disclosed herein is directedto solving radio communications-centric issues and is necessarily rootedin computer technology and overcomes problems specifically arising inradio communications. Moreover, in at least one of its aspects thetechnology disclosed herein improves the functioning of the basicfunction of a wireless terminal and/or node itself so that, for example,the wireless terminal and/or node can operate more effectively byprudent use of radio resources.

Although the description above contains many specificities, these shouldnot be construed as limiting the scope of the technology disclosedherein but as merely providing illustrations of some of the presentlypreferred embodiments of the technology disclosed herein. Thus the scopeof the technology disclosed herein should be determined by the appendedclaims and their legal equivalents. Therefore, it will be appreciatedthat the scope of the technology disclosed herein fully encompassesother embodiments which may become obvious to those skilled in the art,and that the scope of the technology disclosed herein is accordingly tobe limited by nothing other than the appended claims, in which referenceto an element in the singular is not intended to mean “one and only one”unless explicitly so stated, but rather “one or more.” All structural,chemical, and functional equivalents to the elements of theabove-described preferred embodiment that are known to those of ordinaryskill in the art are expressly incorporated herein by reference and areintended to be encompassed by the present claims. Moreover, it is notnecessary for a device or method to address each and every problemsought to be solved by the technology disclosed herein, for it to beencompassed by the present claims. Furthermore, no element, component,or method step in the present disclosure is intended to be dedicated tothe public regardless of whether the element, component, or method stepis explicitly recited in the claims. No claim element herein is to beconstrued under the provisions of 35 U.S.C. 112, sixth paragraph, unlessthe element is expressly recited using the phrase “means for.”

What is claimed is:
 1. A user equipment comprising: receiving circuitryconfigured to: receive, when the user equipment is in Radio ResourceControl connected mode/state, and from a base station apparatus, a radioresource control signaling including an indication, the indication beingused for identifying a synchronization signal block type of asynchronization signal block in which a primary synchronization signal,a secondary synchronization signal, a physical broadcast channel, and areference signal for decoding the physical broadcast channel aretransmitted, the synchronization signal block type being indicated bythe indication, the synchronization signal block consisting of aconstant number of OFDM symbols; and receive, from the base stationapparatus, the synchronization signal block in which the primarysynchronization signal, the secondary synchronization signal, thephysical broadcast channel, and the reference signal for decoding thephysical broadcast channel are transmitted; and processing circuitryconfigured to determine the synchronization signal block type based onthe indication, wherein the processing circuitry is configured to:perform a time and frequency synchronization based on the primarysynchronization signal and the secondary synchronization signal; andobtain System Frame Number information provided by the physicalbroadcast channel.
 2. A base station apparatus comprising: transmittingcircuitry configured to: transmit, when a user equipment is in RadioResource Control connected mode/state, and to the user equipment, aradio resource control signaling including an indication, the indicationbeing used for identifying a synchronization signal block type of asynchronization signal block to which a primary synchronization signal,a secondary synchronization signal, a physical broadcast channel, and areference signal for decoding the physical broadcast channel are mapped,the synchronization signal block type being indicated by the indication,the synchronization signal block consisting of a constant number of OFDMsymbols; and transmit, to the user equipment, the synchronization signalblock to which the primary synchronization signal, the secondarysynchronization signal, the physical broadcast channel, and thereference signal for decoding the physical broadcast channel are mapped,wherein the primary synchronization signal and the secondarysynchronization signal are used for identifying a physical cellidentity, and the physical broadcast channel is used for carrying SystemFrame Number information.
 3. A communication method of a user equipmentcomprising: receiving, when the user equipment is in Radio ResourceControl connected mode/state, and from a base station apparatus, a radioresource control signaling including an indication, the indication beingused for identifying a synchronization signal block type of asynchronization signal block in which a primary synchronization signal,a secondary synchronization signal, a physical broadcast channel, and areference signal for decoding the physical broadcast channel aretransmitted, the synchronization signal block type being indicated bythe indication, the synchronization signal block consisting of aconstant number of OFDM symbols; receiving, from the base stationapparatus, the synchronization signal block in which the primarysynchronization signal, the secondary synchronization signal, thephysical broadcast channel, and the reference signal for decoding thephysical broadcast channel are transmitted; determining thesynchronization signal block type based on the indication; performing atime and frequency synchronization based on the primary synchronizationsignal and the secondary synchronization signal; and obtaining SystemFrame Number information provided by the physical broadcast channel. 4.A communication method of a base station apparatus comprising:transmitting, when a user equipment is in Radio Resource Controlconnected mode/state, and to the user equipment, a radio resourcecontrol signaling including an indication, the indication being used foridentifying a synchronization signal block type of a synchronizationsignal block to which a primary synchronization signal, a secondarysynchronization signal, a physical broadcast channel, and a referencesignal for decoding the physical broadcast channel are mapped, thesynchronization signal block type being indicated by the indication, thesynchronization signal block consisting of a constant number of OFDMsymbols; and transmitting, to the user equipment, the synchronizationsignal block to which the primary synchronization signal, the secondarysynchronization signal, the physical broadcast channel, and thereference signal for decoding the physical broadcast channel, aremapped, wherein the primary synchronization signal and the secondarysynchronization signal are used for identifying a physical cellidentity, and the physical broadcast channel is used for carrying SystemFrame Number information.
 5. The user equipment according to claim 1,wherein the indication indicates to which of all synchronization signalblock types the synchronization signal block belongs, andsynchronization signal blocks of the all synchronization signal blocktypes have a same number of resources.
 6. The base station apparatusaccording to claim 2, wherein the indication indicates to which of allsynchronization signal block types the synchronization signal blockbelongs, and synchronization signal blocks of the all synchronizationsignal block types have a same number of resources.
 7. The communicationmethod according to claim 3, wherein the indication indicates to whichof all synchronization signal block types the synchronization signalblock belongs, and synchronization signal blocks of the allsynchronization signal block types have a same number of resources. 8.The communication method according to claim 4, wherein the indicationindicates to which of all synchronization signal block types thesynchronization signal block belongs, and synchronization signal blocksof the all synchronization signal block types have a same number ofresources.